From: Juri Linkov <juri@jurta.org>
Date: Thu, 2 Sep 2004 09:36:35 +0000 (+0000)
Subject: (Compilation Mode): Add a paragraph about rules
X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~21203
X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=5981c4d02c00e86409b60dd1b4edcedd074933af;p=emacs.git

(Compilation Mode): Add a paragraph about rules
for finding the compilation buffer for `next-error'.
---

diff --git a/man/building.texi b/man/building.texi
index 85240003eec..b3d4659a402 100644
--- a/man/building.texi
+++ b/man/building.texi
@@ -204,6 +204,14 @@ commands advance from there.  When @kbd{C-x `} gets to the end of the
 buffer and finds no more error messages to visit, it fails and signals
 an Emacs error.
 
+  You don't have to be in the compilation buffer in order to use
+@code{next-error}.  If one window on the selected frame can be the
+target of the @code{next-error} call, it is used.  Else, if a buffer
+previously had @code{next-error} called on it, it is used.  Else,
+if the current buffer can be the target of @code{next-error}, it is
+used.  Else, all the buffers Emacs manages are tried for
+@code{next-error} support.
+
   @kbd{C-u C-x `} starts scanning from the beginning of the compilation
 buffer.  This is one way to process the same set of errors again.